test(antithesis): enable forwarder disk persistence#1800
Conversation
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
|
Binary Size Analysis (Agent Data Plane)Baseline: dc62bbd · Comparison: 564e457 · diff ✅ Binary size difference within thresholdChanges by Module
Detailed Symbol Changes |
Regression Detector (Agent Data Plane)Run ID: Optimization Goals: ✅ No significant changes detectedFine details of change detection per experiment (35)Experiments configured
Bounds Checks: ✅ Passed (5)
ExplanationA change is flagged as a regression when |Δ mean %| > 5.00% in the regressing direction for its optimization goal AND SMP marks the experiment as a regression ( |
dd0c580 to
6945527
Compare
04cada1 to
e3b7d43
Compare
6945527 to
6e47ff1
Compare
e3b7d43 to
1d74c55
Compare
6e47ff1 to
b291254
Compare
1a275ee to
52a95f4
Compare
2ac1e74 to
90323e5
Compare
1925259 to
709025d
Compare
5a9453c to
e5880cc
Compare
709025d to
00d479d
Compare
e5880cc to
3662eca
Compare
00d479d to
9c8062a
Compare
3662eca to
648ccda
Compare
9c8062a to
6c92cb7
Compare
…lification bug Sample forwarder_storage_max_size_in_bytes 50/50 on/off with forwarder_storage_path on a persistent compose volume, so the on-disk retry queue and restart-recovery paths run for the first time. BUG this branch surfaces: with persistence on, a network partition fills the disk-backed retry queue, and the forwarder logs error! per failed retry attempt (io.rs:462/472/421). Over a large backlog that is unbounded log amplification — it floods per-moment output, tripping 'very high output ... fail to materialize' at cx=134896 on run 4ecf6d1b, which masks other findings. The same path also opens the non-atomic torn-write hunt at persisted.rs:184 under node termination.
648ccda to
ed10986
Compare
6c92cb7 to
564e457
Compare

Summary
Sample
forwarder_storage_max_size_in_bytes50/50 on/off withforwarder_storage_pathon a persistent compose volume, so the on-disk retry queue and restart-recovery paths run.Bug discovered, with persistence on, a network partition fills the disk-backed retry queue, and the forwarder logs
error!per failed retry attempt. The size of this spew is relative to the size of the inbound backlog.Change Type
How did you test this PR?
References
N/A